v4.1.1

Compare Source

What's Changed

Fixes

• Fix type import specifier dupe by @​AlexJDG in https://github.com/IanVS/prettier-plugin-sort-imports/pull/125
• Fix vue preprocessor may replace wrong code by @​Tanimodori in https://github.com/IanVS/prettier-plugin-sort-imports/pull/135

Docs

• Add plugins config to README by @​IanVS in https://github.com/IanVS/prettier-plugin-sort-imports/pull/114
• recommend using ^react$ for sorting react to the top. by @​willhoney7 in https://github.com/IanVS/prettier-plugin-sort-imports/pull/126

Maintenance and Dependencies

• Update semver by @​useafterfree in https://github.com/IanVS/prettier-plugin-sort-imports/pull/123
• Fix test script on windows by @​Tanimodori in https://github.com/IanVS/prettier-plugin-sort-imports/pull/134
• Upgrade development dependencies by @​IanVS in https://github.com/IanVS/prettier-plugin-sort-imports/pull/128
• Improve CI by @​IanVS in https://github.com/IanVS/prettier-plugin-sort-imports/pull/136
• Regenerate lockfile by @​IanVS in https://github.com/IanVS/prettier-plugin-sort-imports/pull/129

New Contributors

• @​useafterfree made their first contribution in https://github.com/IanVS/prettier-plugin-sort-imports/pull/123
• @​willhoney7 made their first contribution in https://github.com/IanVS/prettier-plugin-sort-imports/pull/126
• @​AlexJDG made their first contribution in https://github.com/IanVS/prettier-plugin-sort-imports/pull/125
• @​Tanimodori made their first contribution in https://github.com/IanVS/prettier-plugin-sort-imports/pull/134

Full Changelog: IanVS/prettier-plugin-sort-imports@v4.1.0...v4.1.1

v1.41.2

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/29123 - [REGRESSION] route.continue: Protocol error (Fetch.continueRequest): Invalid InterceptionId.

Browser Versions

• Chromium 121.0.6167.57
• Mozilla Firefox 121.0
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 120
• Microsoft Edge 120

v1.41.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/29067 - [REGRESSION] Codegen/Recorder: not all clicks are being actioned nor recordedhttps://github.com/microsoft/playwright/issues/290288 - [REGRESSION] React component tests throw type error when passing null/undefined to componenhttps://github.com/microsoft/playwright/issues/2902727 - [REGRESSION] React component tests not passing Date prop valuhttps://github.com/microsoft/playwright/issues/29023023 - [REGRESSION] React component tests not rendering children phttps://github.com/microsoft/playwright/issues/290199019 - [REGRESSION] trace.playwright.dev does not currently support the loading from URL

Browser Versions

• Chromium 121.0.6167.57
• Mozilla Firefox 121.0
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 120
• Microsoft Edge 120

v1.41.0

Compare Source

New APIs

• New method page.unrouteAll([options]) removes all routes registered by page.route(url, handler, handler[, options]) and page.routeFromHAR(har[, options]). Optionally allows to wait for ongoing routes to finish, or ignore any errors from them.
• New method browserContext.unrouteAll([options]) removes all routes registered by browserContext.route(url, handler, handler[, options]) and browserContext.routeFromHAR(har[, options]). Optionally allows to wait for ongoing routes to finish, or ignore any errors from them.
• New option style in page.screenshot([options]) and locator.screenshot([options]) to add custom CSS to the page before taking a screenshot.
• New option stylePath for methods expect(page).toHaveScreenshot(name[, options]) and expect(locator).toHaveScreenshot(name[, options]) to apply a custom stylesheet while making the screenshot.
• New fileName option for Blob reporter, to specify the name of the report to be created.

Browser Versions

• Chromium 121.0.6167.57
• Mozilla Firefox 121.0
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 120
• Microsoft Edge 120

v1.40.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/28319 - [REGRESSION]: Version 1.40.0 Produces corrupted traceshttps://github.com/microsoft/playwright/issues/283711 - [BUG] The color of the 'ok' text did not change to green in the vs code test results sectiohttps://github.com/microsoft/playwright/issues/2832121 - [BUG] Ambiguous test outcome and status for serial mohttps://github.com/microsoft/playwright/issues/28362362 - [BUG] Merging blobs ends up in Error: Cannot create a string longer than 0x1fffffe8 characthttps://github.com/microsoft/playwright/pull/282398239 - fix: collect all errors in removeFolders

Browser Versions

• Chromium 120.0.6099.28
• Mozilla Firefox 119.0
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 119
• Microsoft Edge 119

v1.40.0

Compare Source

Test Generator Update

New tools to generate assertions:

• "Assert visibility" tool generates expect(locator).toBeVisible().
• "Assert value" tool generates expect(locator).toHaveValue(value).
• "Assert text" tool generates expect(locator).toContainText(text).

Here is an example of a generated test with assertions:

import { test, expect } from '@​playwright/test';

test('test', async ({ page }) => {
  await page.goto('https://playwright.dev/');
  await page.getByRole('link', { name: 'Get started' }).click();
  await expect(page.getByLabel('Breadcrumbs').getByRole('list')).toContainText('Installation');
  await expect(page.getByLabel('Search')).toBeVisible();
  await page.getByLabel('Search').click();
  await page.getByPlaceholder('Search docs').fill('locator');
  await expect(page.getByPlaceholder('Search docs')).toHaveValue('locator');
});

New APIs

• Option reason in page.close(), browserContext.close() and browser.close(). Close reason is reported for all operations interrupted by the closure.
• Option firefoxUserPrefs in browserType.launchPersistentContext(userDataDir).

Other Changes

• Methods download.path() and download.createReadStream() throw an error for failed and cancelled downloads.
• Playwright docker image now comes with Node.js v20.

Browser Versions

• Chromium 120.0.6099.28
• Mozilla Firefox 119.0
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 119
• Microsoft Edge 119

v1.39.0

Compare Source

Add custom matchers to your expect

You can extend Playwright assertions by providing custom matchers. These matchers will be available on the expect object.

import { expect as baseExpect } from '@​playwright/test';
export const expect = baseExpect.extend({
  async toHaveAmount(locator: Locator, expected: number, options?: { timeout?: number }) {
    // ... see documentation for how to write matchers.
  },
});

test('pass', async ({ page }) => {
  await expect(page.getByTestId('cart')).toHaveAmount(5);
});

See the documentation for a full example.

Merge test fixtures

You can now merge test fixtures from multiple files or modules:

import { mergeTests } from '@​playwright/test';
import { test as dbTest } from 'database-test-utils';
import { test as a11yTest } from 'a11y-test-utils';

export const test = mergeTests(dbTest, a11yTest);

import { test } from './fixtures';

test('passes', async ({ database, page, a11y }) => {
  // use database and a11y fixtures.
});

Merge custom expect matchers

You can now merge custom expect matchers from multiple files or modules:

import { mergeTests, mergeExpects } from '@​playwright/test';
import { test as dbTest, expect as dbExpect } from 'database-test-utils';
import { test as a11yTest, expect as a11yExpect } from 'a11y-test-utils';

export const test = mergeTests(dbTest, a11yTest);
export const expect = mergeExpects(dbExpect, a11yExpect);

import { test, expect } from './fixtures';

test('passes', async ({ page, database }) => {
  await expect(database).toHaveDatabaseUser('admin');
  await expect(page).toPassA11yAudit();
});

Hide implementation details: box test steps

You can mark a test.step() as "boxed" so that errors inside it point to the step call site.

async function login(page) {
  await test.step('login', async () => {
    // ...
  }, { box: true });  // Note the "box" option here.
}

Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
  ... error details omitted ...

  14 |   await page.goto('https://github.com/login');
> 15 |   await login(page);
     |         ^
  16 | });

See test.step() documentation for a full example.

New APIs

• expect(locator).toHaveAttribute(name)

Browser Versions

• Chromium 119.0.6045.9
• Mozilla Firefox 118.0.1
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 118
• Microsoft Edge 118

v1.38.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/27071 - expect(value).toMatchSnapshot() deprecation announcement on V1.38
https://github.com/microsoft/playwright/issues/27072 - [BUG] PWT trace viewer fails to load trace and throws TypeErrorhttps://github.com/microsoft/playwright/issues/270733 - [BUG] RangeError: Invalid time valuhttps://github.com/microsoft/playwright/issues/2708787 - [REGRESSION]: npx playwright test --list prints all tests twihttps://github.com/microsoft/playwright/issues/27113113 - [REGRESSION]: No longer able to extend PlaywrightTest.Matchers type for locators and pahttps://github.com/microsoft/playwright/issues/271447144 - [BUG]can not display thttps://github.com/microsoft/playwright/issues/2716327163 - [REGRESSION] Single Quote Wrongly Escaped by Locator When Using Unicodehttps://github.com/microsoft/playwright/issues/27181/27181 - [BUG] evaluate serializing fails at 1.38

Browser Versions

• Chromium 117.0.5938.62
• Mozilla Firefox 117.0
• WebKit 17.0

This version was also tested against the following stable channels:

• Google Chrome 116
• Microsoft Edge 116

v1.38.0

Compare Source

UI Mode Updates

1. Zoom into time range.
2. Network panel redesign.

New APIs

• [browserContext.on('weberror')][browserContext.on('weberror')]
• [locator.pressSequentially()][locator.pressSequentially()]
• The [reporter.onEnd()][reporter.onEnd()] now reports startTime and total run duration.

Deprecations

• The following methods were deprecated: [page.type()][page.type()], [frame.type()][frame.type()], [locator.type()][locator.type()] and [elementHandle.type()][elementHandle.type()].
  Please use [locator.fill()][locator.fill()] instead which is much faster. Use [locator.pressSequentially()][locator.pressSequentially()] only if there is a
  special keyboard handling on the page, and you need to press keys one-by-one.

Breaking Changes: Playwright no longer downloads browsers automatically

[!NOTE]
If you are using @playwright/test package, this change does not affect you.

Playwright recommends to use @playwright/test package and download browsers via npx playwright install command. If you are following this recommendation, nothing has changed for you.

However, up to v1.38, installing the playwright package instead of @playwright/test did automatically download browsers. This is no longer the case, and we recommend to explicitly download browsers via npx playwright install command.

v1.37 and earlier

playwright package was downloading browsers during npm install, while @playwright/test was not.

v1.38 and later

playwright and @playwright/test packages do not download browsers during npm install.

Recommended migration

Run npx playwright install to download browsers after npm install. For example, in your CI configuration:

- run: npm ci
- run: npx playwright install --with-deps

Alternative migration option - not recommended

Add @playwright/browser-chromium, @playwright/browser-firefox and @playwright/browser-webkit as a dependency. These packages download respective browsers during npm install. Make sure you keep the version of all playwright packages in sync:

// package.json
{
  "devDependencies": {
    "playwright": "1.38.0",
    "@​playwright/browser-chromium": "1.38.0",
    "@​playwright/browser-firefox": "1.38.0",
    "@​playwright/browser-webkit": "1.38.0"
  }
}

Browser Versions

• Chromium 117.0.5938.62
• Mozilla Firefox 117.0
• WebKit 17.0

This version was also tested against the following stable channels:

• Google Chrome 116
• Microsoft Edge 116

v3.1.0

Compare Source

Minor Changes

• feat: add support for nodejs20.x (#​11067)

v1.30.3

Compare Source

Patch Changes

• fix: correct documentation for beforeNavigate (#​11300)

v1.30.2

Compare Source

Patch Changes

• fix: revert recent 'correctly return 415' and 'correctly return 404' changes (#​11295)

v1.30.1

Compare Source

Patch Changes

• fix: prerendered root page with paths.base config uses correct trailing slash option (#​10763)

• fix: correctly return 404 when a form action is not found (#​11278)

v1.30.0

Compare Source

Minor Changes

• feat: inline response.arrayBuffer() during ssr (#​10535)

Patch Changes

• fix: allow "false" value for preload link options (#​10555)

• fix: call worker unref instead of terminate (#​10120)

• fix: correctly analyse exported server API methods during build (#​11019)

• fix: avoid error when back navigating before page is initialized (#​10636)

• fix: allow service-worker.js to import assets (#​9285)

• fix: distinguish better between not-found and internal-error (#​11131)

v1.29.1

Compare Source

Patch Changes

• fix: correctly return 415 when unexpected content types are submitted to actions (#​11255)

• chore: deprecate preloadCode calls with multiple arguments (#​11266)

v1.29.0

Compare Source

Minor Changes

• feat: add resolveRoute to $app/paths, deprecate resolvePath (#​11261)

v1.28.0

Compare Source

Minor Changes

• chore: deprecate top level promise await behaviour (#​11175)

Patch Changes

• fix: resolve relative cookie paths before storing (#​11253)

• chore: deprecate cookies.set/delete without path option (#​11237)

• fix: make sure promises from fetch handle errors (#​11228)

v1.27.7

Compare Source

Patch Changes

• fix: set runes option in generated root (#​11111)

• fix: retain URL query string for trailing slash redirects to prerendered pages (#​11142)

v1.27.6

Compare Source

Patch Changes

• fix: use runes in generated root when detecting Svelte 5 (#​11028)

• fix: correctly prerender pages that use browser globals and have SSR turned off (#​11032)

• fix: correctly show 404 for prerendered dynamic routes when navigating client-side without a root layout server load (#​11025)

v1.27.5

Compare Source

Patch Changes

• fix: add vite.config.js to included files in generated tsconfig (#​10788)

• fix: cache location.origin on startup (#​11004)

v1.27.4

Compare Source

Patch Changes

• fix: generate __data.json for prerendered pages when SSR is turned off (#​10988)

• chore: add experimental compatibility for Svelte 5 (#​11002)

v1.27.3

Compare Source

Patch Changes

• fix: use correct environment file for rendering spa fallback page (#​10963)

v1.27.2

Compare Source

Patch Changes

• fix: missing File Node polyfill for Node version 18.11.0+ (#​10948)

v1.27.1

Compare Source

Patch Changes

• fix: only apply some polyfills below node 18.11 (#​10920)

v1.27.0

Compare Source

Minor Changes

• feat: add invalidateAll boolean option to enhance callback (#​9889)

v1.26.0

Compare Source

Minor Changes

• feat: infer route parameter type from matcher's guard check if applicable (#​10755)

Patch Changes

• fix: basic mime type handling for prerendered pages in preview (#​10851)

• chore: use just a single library (mrmime) for mime type handling (#​10851)

• chore: bump undici to address security issue (#​10885)

• fix: follow whatwg fetch spec for handling redirect loops (#​10857)

• fix: use window.fetch in load functions to allow libraries to patch it (#​10009)

• chore(deps): update dependency undici to ~5.26.0 (#​10860)

v1.25.2

Compare Source

Patch Changes

• fix: correctly update $page.url.hash when navigating history (#​10843)

• fix: strip virtual module prefix from error messages (#​10776)

• fix: cancel ongoing navigation when the browser back button is hit to prevent an incorrect page from being rendered (#​10727)

• fix: only remove Vite manifest when copying files (#​10782)

v1.25.1

Compare Source

Patch Changes

• fix: correct line numbers in stack trace (#​10769)

• fix: correctly return 404 when navigating to a missing page and the root layout fetches a prerendered endpoint (#​10565)

• fix: allow optional param in middle of route (#​10736)

• chore: update undici (#​10641)

v1.25.0

Compare Source

Minor Changes

• feat: add server endpoint catch-all method handler fallback (#​9755)

Patch Changes

• fix: allow calling fetch for any scheme (#​10699)

v1.24.1

Compare Source

Patch Changes

• fix: mark aborted/cancelled navigation as handled (#​10666)

v1.24.0

Compare Source

Minor Changes

• feat: onNavigate lifecycle function (#​9605)

Patch Changes

• fix: Use Proxy to track usage of client side load event.route (#​10576)

v1.23.1

Compare Source

Patch Changes

• fix: process globs in pkg.workspaces (#​10625)

v1.23.0

Compare Source

Minor Changes

• feat: add warning for mistyped route filenames (#​10558)

• feat: accept URL in redirect (#​10570)

Patch Changes

• fix: adjust the type of Navigation["type"] (#​10599)

• fix: allow logging $page.url during prerendering (#​10567)

v4.1.0

Compare Source

Features

• vitest: add vitest cleanup export (#​294) (ee1b1f7)

v4.0.6

[Compare Source](https://togithub.com/testing-library/svelte-testing-